Connect the shared home through missions, participation and an inclusive Atlas - #10

The homepage now leads into one shared home for discovery and collaboration. Singularity gives each published mission a room for needs, offers and inspectable work, while the homepage and Observatory show a small overview derived from actual public records.

• Add identity-bound participation with private receipts, recovery of own submissions, moderation, closing, withdrawal, fixed expiry and atomic quotas. The additive D1 migration preserves existing identities, proposals and receipts.
• Connect the original event-horizon design to the shared home, retain Canvas motion only on the homepage, and refresh the social preview. The founding mission includes the wellbeing of contributors themselves; Dark remains the default and semantic color roles prepare a future explicit Bright switch.
• Expand the Atlas to 25 source-backed entries, including Codex, Copilot CLI and other open-source and commercial tools, with explicit licensing and access context.
• Publish a roadmap for larger project coordination, artifact receipts, explicit QA acceptance, a guided Solidity contract lab and optional settlement, with primary references and concrete release criteria.
• Correct GitHub identity verification for the Workers runtime: use manual redirects and reject every redirect response. Add explicit manifest/download MIME types and align the versioned security.txt with the existing managed Cloudflare representation.

Validation includes repository/build contracts, 52 invalid-payload and credential-scope cases, 54 real SQLite service tests, controller race/lifecycle checks, deterministic builds and reproducible social-card rendering. Browser checks cover local participation, moderation visibility, closing and withdrawal, mission-to-evidence handoff, real activity counts, Atlas search/comparison, the roadmap and narrow layouts. A deliberately delayed mission response confirms that choosing a review cannot be overwritten. Live GitHub enrollment exposed the Workers redirect incompatibility; final production verification follows deployment.

Deployment order: apply the additive participation migration, deploy all five Worker modules, then publish the exact static artifact. Existing authorization boundaries, sibling sites and provider-managed assets must remain intact. Payments, task execution and automatic assignment are outside this change.